Method of gathering location data of terminals in a communication network

ABSTRACT

The present invention concerns a method of gathering location data of terminals in a communication network, the network comprising at least one location determination functionality adapted to determine data indicative of the location of a specified terminal within said network, and a control functionality adapted to control at least said location determination functionality, said method comprising the steps of: acquiring location data of specified terminals in response to corresponding requests from a service application, monitoring a load condition of said at least one location determination functionality resulting from said acquiring of location data of specified terminals, first detecting that said monitored load condition is below a certain threshold value, second detecting that a predetermined event concerning at least one terminal has occurred, and collecting location data of terminals in response to said second detecting.

FIELD OF THE INVENTION

[0001] The present invention relates to a method of gathering locationdata of terminals in a communication network.

BACKGROUND OF THE INVENTION

[0002] With recent progress in communication technology, servicesoffered by communication network operators to the subscribers theretohave also gained more attention. Among such services, so-called locationbased services (LCS) find considerable attention. For example, asubscriber may have subscribed to a service providing the subscriberwith up-to-date traffic information via the network to his communicationterminal. To this end, however, in order to provide the properinformation to the subscriber, it is inevitable to know the subscriber'slocation within the network. Stated in other words, a subscribercurrently being located in the Berlin area does not need to receivetraffic information concerning the Helsinki area. Likewise, havingsubscribed to a yellow page service requires a knowledge of thesubscriber's position within the network in order to provide him “only”with the relevant yellow page entries.

[0003] As mentioned above, the present invention is concerned to gathersuch location information on the location of a terminal attached and/orregistered to a communication network.

[0004] In this connection, it has to be noted that the present inventionas subsequently described is applicable to any communication network aslong as terminals may change their position within the communicationnetwork. Thus, the network may support the use of e.g. mobile terminalsin the sense of wireless terminals or even some kind of “fixed” (i.e.non-wireless) terminals which may however be connected (“plugged-in”) atdifferent locations within the network. The expression terminal as usedherein is intended to cover any such type of subscriber equipment.Likewise, also the communication network as such is not limited to acertain type of communication network. For purposes of describing thepresent invention, however, the subsequent description refers to a WCDMA(WCDMA=Wideband Code Divisional Multiple Access) radio communicationnetwork also known as 3G UMTS (3G=3^(rd) generation, UMTS=UniversalMobile Telecommunication System) network. Nevertheless, othercommunication networks based on other or similar transmission principles(such as FDMA (Frequency Division Multiple Access) and/or TDMA (TimeDivision Multiple Access) are also suitable for the present inventionbeing implemented thereto.

[0005]FIG. 1 shows a typical example of at least those parts of thecommunication network architecture which are involved when the presentinvention is implemented to the communication network. The illustratedexample in FIG. 1 refers to the 3G UMTS network architecture.

[0006] As shown, a terminal also known as user equipment UE is adaptedto communicate via the network. Note that for communication the userequipment UE has at least to be registered to the network in asubscriber database (HLR/HSS) and attached to a communication network.“Attached” here means a state of the user equipment in which it isswitched on and it is known to the network that the user equipment UEterminal is (in principle) “ready” for communication even if currentlyidle.

[0007] In communication, the user equipment UE accesses the networkinfrastructure via an air interface (not expressly shown). Moreprecisely, the terminal UE exchanges signals with a radio transceiverdevice referred to as Node_B (in UMTS) (corresponding to Base Station BSin GSM). Each Node_B has a certain coverage area within whichcommunication with the Node_B is enabled. The coverage area is alsoreferred to as a cell. Each cell is identified by at least a cellidentifier. Optionally, a cell identifier CI can be supplemented by alocation area identifier LAI. The entire communication network area isthus composed of a plurality of cells. The location of Node_B's isdefined upon network planning. Thus, a network management/planningsystem functional entity has a knowledge of the network topology andalso of the cell identifiers corresponding to the respective Node_B's.

[0008] A group of Node_B's are controlled by a radio network controllerRNC (corresponding to base station controller BSC in GSM). Of course,although not shown in FIG. 1, more than one RNC can be present in thenetwork depending on its size/area covered. In order to keep theillustration simple, however, only one RNC has been shown. Note that aRNC represents an access control entity of said network, which iscurrently in charge of controlling access-of said terminal to saidnetwork.

[0009] Further, one or more RNC's are grouped for being controlled by amobile services switching center MSC (3G-MSC) serving as a routingentity currently in charge of routing messages for said terminal. Thismeans that the MSC switches calls/connections concerning a terminal ofinterest in that the MSC “selects” the proper RNC controlling the properNode_B via which the terminal communicates. Depending on the size of thenetwork, of course more than one MSC are present. A moving and/orroaming terminal may thus be present in the area of a MSC which may alsobe referred to as “visited MSC” VMSC. Associated to a VMSC there is aVLR (Visitor Location Register (in GSM) or its 3G equivalentfunctionality.

[0010] Note that in 3G UMTS networks not only speech (as an example ofreal-time data) are transmitted, but also packet data (as an example onnon-real-time data) are transmitted. Packet data transmission takesplace via a so-called GPRS (General Packet Radio Service) networkexisting “in parallel” and comprising SGSN (Serving GPRS Support Node)and GGSN (Gateway GSN) nodes. In the GPRS, the SGSN corresponds infunctionality and hierarchical location within the network to the VMSCexplained above.

[0011] Connected to the MSC/SGSN (which in FIG. 1 are shown asdistributed entities) is a location determination functional entity SMLCwhich as shown is located in close relation to the RNC (although this isnot absolutely necessary). A distributed SMLC may also be directlyconnected to the Node_B's. The MSC/SGSN and SMLC may in turn beconnected to a gateway entity GMLC (Gateway Mobile Location Center). TheSMLC, MSC/SGSN may further be connected to the networkplanning/management system mentioned earlier above (NetAct). Note thatNetAct is a product name of a product of the applicant, which productname denotes an example product of a system provisioned with networkmanagement functionalities and/or a network management system. Thus, anymention of NetAct is intended as an example of such a product and refersin general to a network management system without restricting it to theactual product NetAct.

[0012] Also, it is to be noted that any network planning is effected interms of network optimization. Hence, any reference to a networkplanning method/system of course implies that network optimization isinvolved in planning.

[0013] The GMLC has a connection to a subscriber register HLR (HomeLocation register) and/or HSS (Home Subscriber Server) keeping a recordof subscribers having subscribed to the network and the servicesavailable to them. In addition, the GMLC provides for a gatewayfunctionality offering a connection to the “outside” of the network,where an application (e.g. run on a computer device) is located. (Theapplication may be associated to a service control point entity SCP ofthe network (not shown).)

[0014] Signaling between GMLC-SMLC and SMLC-MSC/SGSN is, for example,achieved using MAP3/SS7 (Mobile Application Part 3/Signaling System No.7) in circuits switched as well as in packet switched networks, as shownin FIG. 1.

[0015] Note that the entirety of the SMLC, GMLC and other networkelements such as middleware components and interfaces involved indetermination of the position of terminals is also referred to as“positioning estimation and information machine” and/or locationdetermination functionality in the context of the present application.The location determination functionality is under control of anassociated control functionality adapted to control at least saidlocation determination functionality, and which control functionality(not separately shown in FIG. 1) may be spatially concentrated at theSMLC and/or GMLC or spatially distributed within the network.

[0016] So far, the network architecture has roughly been described inorder to simplify understanding of the invention. Of course, theentities described above may perform additional. functions as comparedto those briefly highlighted above. However, a full description of thecapabilities and interrelations and the interfaces there between can notbe given in the framework of the present patent application. Rather, thereader is referred to the corresponding standards published by 3GPP(3^(rd) Generation Partnership Project) and/or ETSI (EuropeanTelecommunication Standards Institute).

[0017] In a further approach, the applicant of the present inventionconceived to fetch network parameters from the base station controllerBSC and/or radio network controller RNC using location based servicesLCS standard messages. (Note that with Camel ATI mentioned earlier aboveonly Cell ID or SAI can be fetched from MSC/SGSN.)

[0018] The 3GPP standards are describing in a very detailed manner avariety of positioning methods and their retrieval methods. In additionto those, there might be vendor specific enhanced non-standard methods.This invention is not limited to a particular method nor is it importantto understand whether the radio network or the terminal are answeringeither x, y coordinates or proprietary messages via the circuit switchedor packet switched core network to the requesting entity, which could beGMLC or MSC. The location determination functionality and especially theSMLC functionality as such can be distributed throughout the networkproviding the x,y coordinates one way or another.

[0019] In general, location data of specified terminals is acquired inresponse to corresponding requests from a service application. However,for the present invention it is not crucial in which specific way theposition information related to a specified terminal is determined aslong as it is determined by means of the location determinationfunctionality.

[0020] Acquiring the location data by means of the locationdetermination functionality requires quite some processing capacity dueto signaling/calculating to be performed in connection therewith. Theentire location determination functionality has therefore beendimensioned to get along with a specified maximum of locationdetermination requests that can be expected to simultaneously occur inpractice.

[0021] This rated (maximum) processing capacity, however, is notconstantly used as the maximum number of requests is not constantlyreached but occurs rather seldom. Hence, at least part of the overallavailable processing capacity of the location determinationfunctionality remains unused most of the time.

[0022] From an economical point of view, this is, however, inconvenientfor a network operator having provisioned his network with a locationdetermination functionality.

SUMMARY OF THE INVENTION

[0023] Consequently, it is an object of the present invention to providea method of gathering location data of terminals in a communicationnetwork which is free from the above mentioned drawbacks.

[0024] According to the present invention, this object is for exampleachieved by method of gathering location data of terminals in acommunication network, the network comprising at least one locationdetermination functionality adapted to determine data indicative of thelocation of a specified terminal within said network, and a controlfunctionality adapted to control at least said location determinationfunctionality, said method comprising the steps of: acquiring locationdata of specified terminals in response to corresponding requests from aservice application, monitoring a load condition of said at least onelocation determination functionality resulting from said acquiring oflocation data of specified terminals, first detecting that saidmonitored load condition is below a certain threshold value, seconddetecting that a predetermined event concerning at least one terminalhas occurred, and collecting location data of terminals in response tosaid second detecting.

[0025] Also, according to the present invention, this object is forexample achieved by a system for gathering location data of terminals ina communication network, the network comprising at least one locationdetermination functionality adapted to determine data indicative of thelocation of a specified terminal within said network, and a controlfunctionality adapted to control at least said location determinationfunctionality, said system comprising: an acquisition functionalityadapted to acquire location data of specified terminals in response tocorresponding requests from a service application, said controlfunctionality comprising a monitoring means adapted to monitor a loadcondition of said at least one location determination functionalityresulting from said acquiring of location data of specified terminals, afirst detection means adapted to detect that said monitored loadcondition is below a certain threshold value, a second detection meansadapted to detect that a predetermined event concerning at least oneterminal has occurred, and a collection functionality adapted to collectlocation data of terminals in response to said second detecting.

[0026] According to advantageous further refinements of the presentinvention (method and/or system),

[0027] said threshold value is defined as a percentage of the maximumprocessing capacity of said at least one location determinationfunctionality,

[0028] said threshold value is predefined and fixed,

[0029] said threshold value is dynamically defined,

[0030] said threshold value varies dependent on time,

[0031] said predetermined event concerns an arbitrary one of terminalsregistered to said network,

[0032] said predetermined event comprises at least one network conditionto be exploited for network management and optimization purposes,

[0033] said predetermined event comprises at least one of the followingconditions terminal requesting active set update, terminal performingintersystem handover, terminal performing traffic reason handover,terminal with frequent handovers, terminal commanded to reduce bit rate,terminal using a specified service,

[0034] collected location data of terminals is statistical data,

[0035] said collected location data of terminals are subjected to afurther step of removing terminal identification information so as to berepresented anonymously,

[0036] an event is judged to have occurred if said condition isfulfilled for at least a predetermined minimum number of arbitraryterminals,

[0037] said predetermined event is the lapse of a predetermined periodof time,

[0038] said threshold value varies dependent on the monitored loadcondition,

[0039] for network management purposes the location of terminals isanalyzed per event or combinations of events.

[0040] Accordingly, by virtue of the present invention being implementedin a communication network and/or the control functionality of thelocation determination functionality, the following advantages can berealized:

[0041] the usage of the overall available processing capacity of thelocation determination functionality is optimized, in that sparecapacity of the network (i.e. the location determination functionality)is used to provide additional information on the location of terminalsto be exploited for e.g. network optimization,

[0042] a network operator having provisioned his network with a locationdetermination functionality may use this functionality with increasedeconomical efficiency, since the location data of terminals collected inresponse to said second detecting can be used for other purposes such asnetwork planning and optimization,

[0043] the collected location information is statistical and anonymousand does not cause additional costs to the subscriber/user of aterminal,

[0044] due to using the collected data for network planning andoptimization, the costs for running the network can be reduced,

[0045] the optimization process can be based on a new dimension and/orvariable, i.e. location, which offers more precise information (withhigher spatial resolution) as compared to the former cell-based networkoptimization,

[0046] no additional hardware/software costs will arise for the networkoperator, since the location determination functionality is alreadyimplemented in the network while its usage is only optimized accordingto the present invention,

[0047] the present invention is applicable to any communication systemutilizing a terminal location determination functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The present invention is subsequently described in greater detailwith reference to the accompanying drawings, in which:

[0049]FIG. 1 shows a typical example of at least those parts of thecommunication network architecture which are involved when the presentinvention is implemented,

[0050]FIG. 2 illustrates a diagram showing the location determinationfunctionality's load (“SMLC load”) versus time,

[0051]FIGS. 3 and 4, respectively, show in rough outline entities and/orgroups of entities in connection with the present invention andinterfaces there between, used for explaining a basic signalingscenario.

DETAILED DESCRIPTION OF THE EMBODIMENTS

[0052] The present invention will be more readily understood whenreferring to the following detailed description thereof in conjunctionwith the accompanying drawings.

[0053] In brief, according to the present invention, spare capacity ofthe Gateway Mobile Location Center (GMLC), Serving Mobile LocationCenter (SMLC), interfaces and other positioning related network elements(NE) and/or other functional entities, in their entirety referred to aslocation determination functionality, is used effectively in the networkoptimization process. The Serving Mobile Location Center SMLC describesa functional block that provides location information to location-basedservices. The SMLC computes the location coordinates (e.g.latitude/longitude) of a subscriber's handset/terminal. The GMLC is agateway that receives the mobile position information from the networkand transfers the information to the location applications involved. TheGMLC receives the location queries/requests from (authorized)applications, processes them, and replies with the position information.Enabling Mobile Location Center (EMLC) or other middleware componentscan have the capability to translate it to location area information(such as city name or postal code) from position data. Further, thoseentities interface to other positioning related elements and ensuredifferent positioning related tasks such as security, privacy andcollecting history into database etc. However, these related tasks suchas security, privacy are not relevant as such for the present inventionand a description thereof is therefore omitted. In connection with thepresent invention, it is proposed that the SMLC (and other relevantnetwork elements for the location determination process) is providedwith performance counters (and/or performance measurement units), whichinform about the utilization level of the relevant network elements.Furthermore it is proposed that one or more configuration parameter(s)(referred to as load condition threshold value) (which can be a constantvalue, say e.g. 70% of the rated processing capacity, or can be defineddynamically as a function of e.g. time) is introduced to provide areference for the load condition of the location determinationfunctionality, under which threshold value event triggered positioning,e.g. for network optimization purposes, is possible. The list of such“events” can be endless. For example, an event may reside in mobilestation requesting active set update, mobile station performingintersystem handover (HO), mobile station performing traffic reason HO,mobile station with frequent HOs, mobile station commanded to reduce bitrate, mobile station using a specific service (for example, a servicecan be a UMTS traffic class, a certain PDP context, possibly also someend-to-end service like yellow pages, pizza service or the like). (thismeasurement is important information source in terms of coverage areavs. served bit rate/service). The above list of events is intended as anexample only and not limiting the events applicable in connection withthe present invention. Practically, any event which may occur inconnection with a terminal registered/attached to a communicationnetwork may be exploited as an event triggering collecting of locationdata of terminals in response to said triggering. The informationcollected is “statistical”, i.e. not IMSI (International MobileSubscriber Identity) and/or IMEI (International Mobile EquipmentIdentity) specific. Stated in other words, the collected information isanonymous. This in turn means that for example the collected informationis represented as colored areas on a network map where a certain servicewas used or where handover triggering happened, but we do not know whowas using the service/who was commanded to handover. Also, an event assuch as mentioned above may be combined with a threshold number ofterminals for which said event occurred. Note that “SMLC” is to beunderstood that it contains all entities, interfaces, HW, SW etc.related to the positioning estimation and the delivery of thepositioning information. In real implementation it can be that severallocation related load indicators are monitored as the locationdetermination functionality may be provisioned in the networkcentralized or spatially distributed. The optimizer and/or networkplanning and management system is utilizing the existing network andposition estimate & information machine consisting of entities such asGMLC, SMLC, interfaces, middleware and other functional blocks in orderto optimize the network with the usage of collected terminal locationinformation. The optimizer is providing event thresholds and/or triggersto the network, so that the network can inform the locationdetermination functionality about the occurrence of those events (i.e.request collecting of location information). The events are thentriggering the location determination functionality to calculate theactual terminal position in case of “free” processing capacity (belowthe load threshold). The event related position is fed back to theoptimizer. Now the optimizer uses the information for networkoptimization. The service order related position can be understood asthe terminal position when the service was requested or it can beperiodic UE position information, which is provided as a part of theservice. Services, which are based on events or periodic locationinformation, can also be used to retrieve terminal location for thepurpose of network optimization. It is to be noted that the optimizerfunctionalities may be in a network management system, but also in abase station controller BSC and/or a radio network controller RNC (orother relevant network element).

[0054]FIG. 2 illustrates a diagram showing the location determinationfunctionality's load (“SMLC load”) versus time. The SMLC load heredenotes the load of the location determination functionality. This meanseither the processing load for the entirety of involved entities, or theprocessing load imposed on a part of the entirety (e.g. in case ofspatially distributed location determination functional entities. Amaximum SMLC processing capacity (rated capacity) is denoted bymaxSMLCcapacity and indicated by a broken line. Below said maximum, athreshold level indicated by a dotted line is defined, the thresholdbeing used for event triggered location determination. Said thresholdvalue is defined as a percentage of the maximum processing capacity ofsaid at least one location determination functionality. Note thatalthough the expression “percentage” is used herein, it is intended todenote in general a share or portion of the maximum processing capacitywhich need not necessarily be expressed in percents. According to FIG.2, said threshold value is predefined and fixed. Nevertheless, accordingto a modification (not shown) it is possible to define said thresholdvalue dynamically. In such a case, said threshold value varies forexample dependent on time (the variation may be stepwise or gradually).Additionally or alternatively, said threshold value may vary dependenton the monitored load condition.

[0055] The processing load is composed of two components.

[0056] One component is the processing load originating from locationdetermination requests issued by location based services LCS. Thiscomponent is indicated by the individual bars represented with abrickwall pattern in FIG. 2. Based on these requests, the locationdetermination functionality acquires location data of specifiedterminals in response to corresponding requests from a serviceapplication. A specified terminal here means an identified terminal(e.g. by its IMSI or IMEI or any other identification information).

[0057] The second component is the processing load originating fromevent triggered location determination. The second component may,however, only be present in case the first component does not exceed thethreshold level. That is, while acquiring location data of specifiedterminals in response to corresponding requests from a serviceapplication, there is performed a monitoring of the load condition ofsaid at least one location determination functionality which resultsfrom said acquiring of location data of specified terminals. Also, thereis performed a first detecting that said monitored load condition isbelow a certain threshold value. If so, there is performed a seconddetecting that a predetermined event concerning at least one terminalhas occurred, and collecting location data of terminals is performed inresponse to said second detecting. The second component is illustratedas a hatched portion in the diagram shown in FIG. 2.

[0058] Practically, any event which may occur in connection with aterminal registered/attached to a communication network may be exploitedas an event triggering/initiating collecting of location data ofterminals as long as said predetermined event comprises at least onenetwork condition of interest for/to be exploited for network managementand optimization purposes. In particular, those events as listed abovemay be used in said second detecting. The predetermined event mayconcern an arbitrary one of terminals registered to said network.Nevertheless, an event may be judged to have occurred, if the conditionis fulfilled for at least a predetermined minimum number of arbitraryterminals. Also, the event may reside in the lapse of a predeterminedperiod of time.

[0059] As a result of collecting location data of terminals, statisticaldata of location data of terminals is obtained. This means that saidcollected location data of terminals are subjected to a further step ofremoving terminal identification information so as to be representedanonymously.

[0060] Then, the collected data can be graphically represented as one ormore maps showing a spatial distribution of respective events, even witha sub-cell resolution. Stated in other words, for network managementpurposes the location of terminals is analyzed per event, or combinationof events. This does not only enable network optimization on a celllevel, but also a network optimization which takes into account thespecific situation due to a terminal distribution within a respectivecell. By means of such a representation, so-called “hot-spots” forspecified events can be discovered within the network and suitablecountermeasures can be initiated in terms of network planning andmanagement to “smoothen” and/or improve the situation in the“hot-spots”. It is to be noted that network planning does not representthe sole field of usage of the collected location information, ratherthese could also be used for business planning purposes and the like.

[0061] As shown in FIG. 2, nearly all the time the processing capacityof the SMLC can be used up to the threshold for both purposes, acquiringlocation data of specified terminals in response to correspondingrequests from a service application as well as collecting (statistical)location data of terminals. Only in case the processing load exceeds thethreshold level already because of requests originating from locationbased services, collecting of statistical location data is prevented inorder to assure proper functioning of the location based services. Therange between the threshold and the maximum capacity can be regarded asa safety margin in order to get along also with peaks in requests oflocation based services.

[0062]FIGS. 3 and 4, respectively, show in rough outline entities and/orgroups of entities in connection with the present invention andinterfaces there between, used for explaining a basic signalingscenario. It is to be noted that this illustration is a simplifiedrepresentation of FIG. 1 and the entities shown in FIGS. 3 and 4 areslightly re-grouped and summarized for explanatory purposes.

[0063]FIGS. 3 and 4 each shows a network management/planning systemdenoted by NetAct/optimizer, which is adapted to use also event relatedterminal location data (apart from “conventional” data (without terminallocation information) obtained for network planning purposes). TheNetAct/optimizer is adapted to communicate with the communicationnetwork/terminals via a first interface, and with the location detectionfunctionality via a third interface. A second interface is provisionedbetween the communication network and the location detectionfunctionality. A fourth interface is provisioned between the locationdetection functionality and applications.

[0064] Now the signaling involved in connection with the presentinvention will be roughly described.

[0065]FIG. 3 represents the signaling in connection with the collectingof event related terminal locations. Initially, the NetAct/optimizerinforms the network via the first interface of the event and/or eventsto be detected, S30: “event order”. In this regard, an event manager isused to order the event e.g. Soft Handover—when such an event occurs forterminal(s), the telecommunication network:

[0066] in case A—is requesting the position of those terminals from thelocation determination functionality (S31). The location determinationfunctionality is checking the load of its elements and is performing thecalculation if the load is below threshold. In case the load is abovethe threshold and the calculation can not be performed, it is possibleto use a negative acknowledgement (S32).

[0067] in case B—will verify free capacity from the locationdetermination functionality before the request of the location (S31).The location determination functionality will acknowledge positive ornegative dependent whether the load is above or below the threshold(S32). In case of a positive answer meaning the location determinationfunctionality has free capacity, the telecom network will send thelocation request of the terminal(s) to the location determinationfunctionality (S33). The position of the terminals can be sent eitherdirectly to the NetAct (S34) or via the telecom network (S36) to theNetAct (S31 a). The combination of the event(s) and the positioninformation is done by NetAct/optimizer e.g. via GIS (GeographicInformation System).

[0068] Upon occurrence of said event, the network informs the locationdetermination functionality via the second interface of the detectedevent, S31. Optionally, in a step S31 a, also the NetAct/optimizer isinformed via the first interface of the occurrence of the event. Sincethe location determination functionality (more precisely, its controlfunctionality) monitors a load condition of said one locationdetermination functionality resulting from acquiring of location data ofspecified terminals (to be described with reference to FIG. 4), itperforms first detecting that the monitored load condition is below acertain threshold value. If this is confirmed, the information on theoccurrence of the event (S31), triggers and/or initiates the seconddetecting that a predetermined event concerning at least one terminalhas occurred, and the collecting of location data of terminals inresponse to said second detecting, S32. Event related information, whichis used in the location determination functionality to determine theposition, are then supplied, S33, via the second interface from thenetwork to the location determination functionality and further via thethird interface from the location determination functionality to theNetAct/optimizer, S34.

[0069] The applications are not directly involved in this scenario,while it has to be kept in mind that requests for location determinationof specified terminals from the applications via the fourth interface tothe location determination functionality, S35, contribute to an increasein the processing load of the location determination functionality.

[0070] Namely, as shown in FIG. 4, requests for location determinationof specified terminals are issued from the applications via the fourthinterface to the location determination functionality, S40 (similar toS35), and contribute to an increase in the processing load of thelocation determination functionality. The location determinationfunctionality requests the position related information. Thisinformation is used in the location determination functionality toconclude the location/position of the specified terminal from thenetwork, S41, which returns the necessary information, S42 to thelocation determination functionality which on the basis thereofdetermines the location of the specified terminal. Thedetermined/acquired location is then supplied to the requestingapplication, S43. On the other hand, the identification information isremoved from this location information and the determined/acquiredlocation in anonymous form is also supplied to the NetAct/optimizer,S44.

[0071] Note that in practice both scenarios as described in connectionwith FIGS. 3 and 4 are simultaneously active in the network, while theirdescription has been separated for explanatory purposes only.

[0072] Although herein above the present invention has mainly beendescribed with a focus on a method, it is to be understood that thepresent invention also concerns a system for gathering location data ofterminals in a communication network, the network comprising at leastone location determination functionality adapted to determine dataindicative of the location of a specified terminal within said network,and a control functionality adapted to control at least said locationdetermination functionality, said system comprising: an acquisitionfunctionality adapted to acquire location data of specified terminals inresponse to corresponding requests from a service application, saidcontrol functionality comprising a monitoring means adapted to monitor aload condition of said at least one location determination functionalityresulting from said acquiring of location data of specified terminals, afirst detection means adapted to detect that said monitored loadcondition is below a certain threshold value, a second detection meansadapted to detect that a predetermined event concerning at least oneterminal has occurred, and a collection functionality adapted to collectlocation data of terminals in response to said second detecting.

[0073] Of course, the monitoring and/or first/second detection means maybe realized in hardware or software.

[0074] Accordingly, gathering of the positioning data according to thepresent invention is preferably event triggered and the combination ofthe event and the position data is used for network optimization orother purposes. Furthermore, the event triggering is preferably onlyused when the positioning machine is not otherwise “busy”, “busy” beingjudged according to a configuration parameter (threshold) which can beadjusted by Operator/client/ . . . or it can be set automatically basedon collected experiences. According to the present invention, theposition information is used in the optimization, while no additionalcosts are caused.

[0075] It should be noted that the network elements (like SGSN, GGSN,GMLC, SMLC etc . . . ) are not limiting the scope of the invention, andit does not matter what the “positioning machine”/location determinationfunctionality consists of, as long as such a functional entity (whichmay even be distributed) exists and there is a means to detect theloading of the entity. Also, the optimizer is the entity that could usethe gathered/collected information, it can be at RNC, BSC or at networkmanagement system (NMS) The gathered information can be used not only inoptimization, but also Operators' business planning, and so on.

[0076] Accordingly, as has been described herein above, the presentinvention concerns a method of gathering location data of terminals in acommunication network, the network comprising at least one locationdetermination functionality adapted to determine data indicative of thelocation of a specified terminal within said network, and a controlfunctionality adapted to control at least said location determinationfunctionality, said method comprising the steps of: acquiring locationdata of specified terminals in response to corresponding requests from aservice application, monitoring a load condition of said at least onelocation determination functionality resulting from said acquiring oflocation data of specified terminals, first detecting that saidmonitored load condition is below a certain threshold value, seconddetecting that a predetermined event concerning at least one terminalhas occurred, and collecting location data of terminals in response tosaid second detecting.

[0077] Although the present invention has been described herein abovewith reference to its preferred embodiments, it should be understoodthat numerous modifications may be made thereto without departing fromthe spirit and scope of the invention. It is intended that all suchmodifications fall within the scope of the appended claims.

1. A method of gathering location data of terminals in a communicationnetwork, the network comprising at least one location determinationfunctionality adapted to determine data indicative of the location of aspecified terminal within said network, and a control functionalityadapted to control at least said location determination functionality,said method comprising the steps of: acquiring location data ofspecified terminals in response to corresponding requests from a serviceapplication, monitoring a load condition of said at least one locationdetermination functionality resulting from said acquiring of locationdata of specified terminals, first detecting that said monitored loadcondition is below a certain threshold value, second detecting that apredetermined event concerning at least one terminal has occurred, andcollecting location data of terminals in response to said seconddetecting.
 2. A method according to claim 1, wherein said thresholdvalue is defined as a percentage of the maximum processing capacity ofsaid at least one location determination functionality.
 3. A methodaccording to claim 2, wherein said threshold value is predefined andfixed.
 4. A method according to claim 2, wherein said threshold value isdynamically defined.
 5. A method according to claim 4, wherein saidthreshold value varies dependent on time.
 6. A method according to claim1, wherein said predetermined event concerns an arbitrary one ofterminals registered to said network.
 7. A method according to claim 1,wherein said predetermined event comprises at least one networkcondition to be exploited for network management and optimizationpurposes.
 8. A method according to claim 1 or 7, wherein saidpredetermined event comprises at least one of the following conditionsterminal requesting active set update, terminal performing intersystemhandover, terminal performing traffic reason handover, terminal withfrequent handovers, terminal commanded to reduce bit rate, terminalusing a specified service.
 9. A method according to claim 1, whereincollected location data of terminals is statistical data.
 10. A methodaccording to claim 9, wherein said collected location data of terminalsare subjected to a further step of removing terminal identificationinformation so as to be represented anonymously.
 11. A method accordingto claim 8, wherein an event is judged to have occurred if saidcondition is fulfilled for at least a predetermined minimum number ofarbitrary terminals.
 12. A method according to claim 1, wherein saidpredetermined event is the lapse of a predetermined period of time. 13.A method according to claim 4, wherein said threshold value variesdependent on the monitored load condition.
 14. A method according toclaim 7, wherein for network management purposes the location ofterminals is analyzed per event or combinations of events.
 15. A systemfor gathering location data of terminals in a communication network, thenetwork comprising at least one location determination functionalityadapted to determine data indicative of the location of a specifiedterminal within said network, and a control functionality adapted tocontrol at least said location determination functionality, said systemcomprising: an acquisition functionality adapted to acquire locationdata of specified terminals in response to corresponding requests from aservice application, said control functionality comprising a monitoringmeans adapted to monitor a load condition of said at least one locationdetermination functionality resulting from said acquiring of locationdata of specified terminals, a first detection means adapted to detectthat said monitored load condition is below a certain threshold value, asecond detection means adapted to detect that a predetermined eventconcerning at least one terminal has occurred, and a collectionfunctionality adapted to collect location data of terminals in responseto said second detecting.
 16. A system according to claim 15, whereinsaid threshold value is defined as a percentage of the maximumprocessing capacity of said at least one location determinationfunctionality.
 17. A system according to claim 16, wherein saidthreshold value is predefined and fixed.
 18. A system according to claim16, wherein said threshold value is dynamically defined.
 19. A systemaccording to claim 18, wherein said threshold value varies dependent ontime.
 20. A system according to claim 15, wherein said predeterminedevent concerns an arbitrary one of terminals registered to said network.21. A system according to claim 15, wherein said predetermined eventcomprises at least one network condition to be exploited for networkmanagement and optimization purposes.
 22. A system according to claim 15or 21, wherein said predetermined event comprises at least one of thefollowing conditions terminal requesting active set update, terminalperforming intersystem handover, terminal performing traffic reasonhandover, terminal with frequent handovers, terminal commanded to reducebit rate, terminal using a specified service.
 23. A system according toclaim 15, wherein collected location data of terminals is statisticaldata.
 24. A system according to claim 23, wherein said collectedlocation data of terminals are subjected to a further step of removingterminal identification information so as to be represented anonymously.25. A system according to claim 22, wherein an event is judged to haveoccurred if said condition is fulfilled for at least a predeterminedminimum number of arbitrary terminals.
 26. A system according to claim15, wherein said predetermined event is the lapse of a predeterminedperiod of time.
 27. A system according to claim 18, wherein saidthreshold value varies dependent on the monitored load condition.
 28. Asystem according to claim 21, wherein for network management purposesthe location of terminals is analyzed per event or combinations ofevents.